Interaction with Spatial Databases

Working with Spatial Databases is only available with the Bentley Map and Bentley Map Enterprise editions of this product. The Bentley Map PowerView edition only allows the Spatial Database import and query capabilities.

This section describes the basic concepts of working with a spatial database such as Oracle or SQL Server. In general, once the connection has been made to the database, the operation is the same regardless of database.

The currently supported spatial databases are:

Oracle Spatial	Editable
SQL Server Spatial	Editable
WFS	Read only

Where there are differences in operation among the supported spatial databases, a separate entry will explain how the operation works with each one.

When a connection is made to a spatial database, all queries are handled by the spatial database. That means Bentley Map can handle very large queries and very large result sets. If a Search is made on the spatial database, the result set is displayed in the Data Browser. As more rows are requested by paging down in the Data Browser, then those rows are sent by the database server.

When operations such as sorting and filtering are performed on the result set in the Data Browser, those operations are actually performed by the database and the results returned to the Data Browser.

This direct connection with the database server lets Bentley Map handle a very large number of rows quickly and efficiently.

Note: Editing of spatial databases is best accomplished with a Bentley Mapproject and a defined spatial data source. Use the Geospatial Administrator to define the spatial data source and register features. The defined spatial data source can be opened from the Map Interoperability dialog as shown.

The interface shows a Spatial Data Source called citygml is defined for this project.